"The trust relationship between this workstation and primary domain failed". Is this a bug in Windows 7
I realize that this is a frequent problem to many user domain environment. I started a new job as the Senior Network Administrator and this error as presented itself to me 5 times within one month. Is this a bug in Windows 7? This did not happen on Windows XP clients machines. I need to find out from Microsoft if there will be a solution for this in future patches or fixes. I would love a prompt response from a Microsoft representative. Users are disliking Windows 7, because of this problem. Thanks in advance.George Mason BSc. MIS, MCP
September 9th, 2010 8:52pm

I have a similar problem with windows 7 in domain being able to see shared folders. I have tried all the online solutions and nothing works. So i've been formatting couple of machines back to XP Pro and it's working fine, lol. What what microsoft will do about this, as i had a plan to upgrade all workstations to windows 7...sad sad
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2010 11:55pm

I have seen this pop up in client logs every once in a while, but it does not seem to cause any issue. We have well over 600 win7 clients deployed here... -Dan
September 10th, 2010 1:43am

Hi, In most situations, we can fix the problem by rejoining the domain. Log on locally as a local administrator. In the Network tool of Control Panel, select Change and enter a Workgroup name, leaving the domain. Restart the computer and log on locally as a local administrator. Then rejoin the domain. There are two methods to rejoin the domain: · You can join the domain from the client if at the same time you can provide an administrator username and password on the domain. -or- · You can delete the existing computer account in Server Manager, recreate the computer account, synchronize the domain, and then on the client rejoin the domain. Also, you can pay attention to the following link, because it would lead to the issue: Error 1789 when you use the LookupAccountName function on a computer that is running Windows 7 or Windows Server 2008 R2 Hope it helps. Regards, Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 14th, 2010 12:29pm

Complimentary to the above post ... a guide http://www.mypchealth.co.uk/Win7Trust.phpwww.mypchealth.co.uk
September 14th, 2010 2:48pm

This issue is not specific to Windows 7. Generally rejoining the computer to the domain resolves the problem. This error indicates that there is a problem between the computer and its account in the domain. Some things to consider... If a user runs the "System Restore" and restores it to an earlier state, this can break the trust with the domain. Also, make sure that if you are imaging, these computers are using SYSPREP correctly. Also, for multi-boot systems, make sure that the different OSs running are using different computer names. Visit: anITKB.com, an IT Knowledge Base.
Free Windows Admin Tool Kit Click here and download it now
September 14th, 2010 4:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics